home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Messages vs. Semaphores for external clocking
- Date: 8 Apr 1996 22:11:45 +0200
- Organization: dis-
- Message-ID: <4kbru1$omt@serpens.rhein.de>
- References: <4ju349$r1e@sparky.navsea.navy.mil> <4jvrqs$hk0@btmpjg.god.bel.alcatel.be> <slN3BCS00iWZ0_8G1R@andrew.cmu.edu> <316533DF.5BFD@bat710.univ-lyon1.fr>
- NNTP-Posting-Host: serpens.rhein.de
-
- Laurent GIROUD <milu28@bat710.univ-lyon1.fr> writes:
-
- > Of course but you must not forget something -> in order to be sure
- >that
- >the semaphore you are just refering to in your program is valid you
- >actually HAVE to FindName() it before and then to acces it in an atomic
- >operation thus needing to embrace the two instructions (FindName +
- >ObtainSemaphore) in a Forbid()/Permit() pair...
-
- No. This is necessary if the semaphore is public and if there is
- no better arbitration protocol for the semaphore.
-
- For tasks that are closely connected you would use a private semaphore
- and a handshake protocol for creation and deletion of the semaphore.
-
- > This could be added to "The OS improvement list" :) ...
-
- Semaphores should be efficient. The validation of a semaphore pointer
- is not efficient and a private semaphore couldn't be validated anyway.
-
- Regards,
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-